How I Converted a Batch Application System to Client-Server and Lived to Tell About It

After years of using mainframe-based batch applications, though they were user-friendly, my users wanted something GUI, something that runs on their desktop, and something that interchanges with their MS-Windows applications. So, I set out to convert my batch application system to something my users wanted. Armed with the SAS System®, Base SAS, SAS/CONNECT®, SAS/AF®, SAS/FSP®, a TCP/IP connection, Windows 98, my large-scale server, my existing batch code, and the will to succeed, I endeavored to build a user-friendly, point-and-click, drag-and-drop, client-server end-user application environment. Now my users can run their favorite end-user applications right from their desktop. They can then use interactive SAS techniques, such as data mining and data visualization, from the results of the applications. And they can import the results into their favorite Windows applications. Within this paper I will describe the steps I took, the tools I used, and the lessons I learned. Special bonus! I will show the SAS code, the SAS/AF Frames, and the SAS Component Language® (SCL®) behind the SAS/AF Frames, and show how all these come together with my data warehouse to create my client-server end-user application environment. This paper is intended for any SAS user who wants to know the possibilities of easy to use end-user applications. Within this paper I do anticipate that the user has some exposure to SAS/AF and SCL.